CK Sector Assault v1.2
By Scott Bruno / Captain Krumb
6/19/2000
*************************************************

This version supports Orion ships (see "CK_OrionSetup" Readme.txt for details) and the sensor H&R detection code. It is otherwise unchanged from the previous version.

DESCRIPTION:
"CK Sector Assault" is a configurable multiplayer mission designed to meet the dynamic needs of campaign scenarios. By using the included Configuration Utility, you can set up a scenario to play out an attack on a sector's military and production assets. This dynamic scenario can include: 

1. Any of the 63 starbase variants in the spec file, including the Orions
2. A planet which can be unarmed, armed with Phaser1 or armed with Phaser4
3. A Shipyard object available in four "classes", from A to D
4. A Fleet Repair Dock
5. Defense Platforms allocated between the base, planet and docks

GAMEPLAY:
There are two teams: Team A, who defends the sector (and controls the starbase, if present) and Team B, who attacks.

Prior to launching the game, the host must run the Configuration Utility ("CK_SectorAssaultConfig.exe") to select the particulars of the scenario. Once that's done, the game is launched and played normally. The mission will appear in the list as "CK Sector Assault 1.0".

NOTE: Race-selection is "manual", instead of automatically matching like host's race like some other scripts do, because manual selection makes it possible to use the Orion entities.

The host of the game will be the one who controls the Starbase. Therefore, someone from the defending team (A) must host the game. To control the Starbase, you select it in the Fleet Control Panel just as you would select control of an AI wingman. You can switch from controlling the Starbase and any ships you might have at will; the AI will automatically take over whichever forces you're not currently controlling.

NOTE: SFC forces you to select at least one ship before it will let you play. If your scenario calls for a sector that does not have any defending ships present, just self destruct the ship and switch over to the base when the mission starts.

HOW TO USE THE BASE:
Controlling a base is very much like controlling a ship. All the familiar systems are there: shields, countermeasures, etc, and all in the same familiar place.

You can control the rotation of the base just like you would turn a ship: by clicking on the 3D screen in the direction you want to rotate. This makes it possible to protect weakened shields and to bring different weapons to bear (although arc coverage of starbase weapons is pretty good all the way around).

Because the large size of a base will probably obscure the normal F3 view, the best view to use is F4. This view is from the target's perspective, and makes it very easy to keep visual track of what's going on.

Because of the large number of weapon systems installed on a full-size Starbase, you might have to use the "Weapons" mode of the Tactical Officer MFD (the topmost panel) in order to see and use them all. For example, the drone racks on the Klingon SBR are not visible in the Ship Schematic & System MFD, but they are visible in the Tactical Officer MFD. To select these weapons, just click on the one you want to fire and hit the 'Z' key like you normally would.

Each base has a default loadout of supplies (various shuttles, drones if you have drone racks, fighters if you're a Hydran, etc) so make sure you take a look and see what you have in stock.

I recommend you play a few practice rounds controlling a base so that you can get familiar with handling it. It's really a lot of fun once you get used to it. You'll especially like the amazing firepower of the larger bases.

DEFENSE PLATFORMS:
Each race has their own version of the Defense Platform. All platforms feature phaser banks. In addition, platforms have one hardpoint of heavy weapons which match that race's heavy weapon. Federation platforms have photons, Klingon & Lyran platforms have disruptors, Rom & Gorn have plasma F, Hydrans have hellbores, and Orions have drone racks.

The platforms will fire both offensively and defensively, providing additional fire on the enemy and point defense against plasma or drones. They have weak shields, but they also have ECM to make up for it.

You have some measure of control over where the Platforms will be allocated. The Configuration Utility will allow you to deploy up to 12 Platforms in the sector, spead out between the Base, Planet and Dock/Shipyard area. NOTE that each object can have a maximum of 4 platforms allocated to it. For example: if you have 7 Platforms in your sector, you might deploy 3 around the base, and the remaining 4 around your shipyard.

SHIPYARDS:
The implementation of Shipyards here is specific to the Starlance SFC campaign. There are four "classes" of Shipyard objects, the lowest being Class D and the highest being Class A. A Shipyard is represented on the screen as one or more Repair Dock objects. To avoid confusion, Shipyards are labelled as such. For example, if you have both a Repair Dock and a Class B Shipyard in the sector, one will say "Class B Shipyard" and the other will say "Fleet Repair Dock".

The objects which make up a given Shipyard entity are "layered" atop one another, and destroying one "layer" reduces that dock's class to the net lowest level (if the last level is destroyed, the Shipyard is totally destroyed). For example: a Class A Shipyard starts with 4 layers. Destroy one and it is downgraded to a Class B. Destroy two, and it becomes Class C. Destroy all four, and the Shipyard is wiped out.

The script allows for one Shipyard object in the sector.

FLEET REPAIR DOCKS:
The script allows you to have Repair Dock (FRD) object as well as a Shipyard. To avoid confusion, FRD's are labelled "Fleet Repair Dock" and are in a different location than the Shipyard. The script allows for a maximum of one FRD object in the sector.

TERRAIN:
There are 6 available map choices: Open Space, Nebula, Asteroids (light), Asteroids (dense), Dust Clouds (light) and Dust Clouds (dense). The map type is selected by the host in the SFC mission setup screen, just as with any other mission.

USING THE CONFIGURATION UTILITY:
The Configuration Utility is what makes the whole thing work. This is the prgram which the host uses to set up the conditions of the scenario; i.e., which race, kind of base, number of platforms, shipyard class, etc. Only the host of the game (who is on the defending Team A) must use the Config program; the other players in the game don't have to do anything special to play.

I tried to design the interface to be as simple as possible. Here's a quick tutorial in its use. 

1. Run the Configuration Program.

2. At the top, the first control you'll see is the control for choosing the race of the base, defsats and other objects. It's labeled, "Select race". Choose the race of the defending team from the list.

3. Beneath that if a group of controls for setting up a planet. The first control is a checkbox which is labelled, "This sector has a planet." If you check that box, the other controls for planet settings will activate. Where it says, "Select planet type", choose the armament/defense level of the planet. If you have Defense Platforms in thee sector and wish to deploy some of the maround the base, check the box which says "Deploy defense platforms for the planet" and then use the up/down arrows to choose a number from 0 to 4. If you change your mind about the number of Platforms, you can change the number at any time. If you decide not to allocate any platforms to the planet, just uncheck the box that says "Deploy defense platforms for the planet." 

4. Under that is a group of controls for setting up a Starbase. The arrangement of controls works in precisely the same way as the planet controls.

5. The next group of controls deals with Shipyards and Repair Docks. If you have either of these objects in the sector, check the appropriate boxes. If you select a Shipyard, use the dop-list control to select its Class (D to A).

6. The last set of controls allows you to deploy some of your Defense Platforms in a protective ring around the Shipyard/Dock area. This is just like deploying Platforms for the planet and base.
Remember that the maximum number of Platforms you can deploy around any individual object is four, and the maximum you can deploy in the sector is 12.

7. Once you're done with your settings, just hit the "OK" button. A message box should pop up and tell you that the data has been saved, and that you may now run the game. Click OK in the messgage box, and the Configuration Program will close.

SCORING:
This mission was left "open" in the sense that there are no game-enforced victory conditions. Since this is designed as a campaign mission, deciding which team "won" the battle is up to the rules of the campaign and the interpretation of the damage inflicted to both sides, and not by SFC's built-in scoring system (which is sort of broken anyway).

That being the case, the mission will not end until you press ESC and choose "End Mission". That way each team can make a proper assessment of damages inflicted, e.g., count the survivors and see how big a chunk you took out of the base. 

Note that you will receive various messages relating to events in the game, e.g., "Damage to the Shipyard has downgraded it to Class C!".


INSTALLATION:
In the .zip file you downloaded, you'll find three files: "readme.txt" (this file), "CK_SectorAssault.scr", and "CK_SectorAssaultConfig.exe".

"CK_SectorAssault.scr" must be copied into the Scripts folder of your SFC installation. Chances are you'll find this folder at C:\Program Files\14 East\SFC\Assets\Scripts. You can either use Windows Explorer to go to this folder, or you can use the Find tool if you have trouble finding it. Once you've located the Scripts folder, copy the .scr file into it. You'll know if you've got the right folder because you should see a bunch of other .scr files there. You'll also know if you've done it right when you get into the game; at the Spacedock screen you should see "CK Starbase Assault 1.1" at the top of the screen.

"CK_SectorAssaultConfig.exe" is the Configuration Utility. You can place this file anywhere you like, but I suggest someplace easy to find like the Desktop.

REQUIREMENTS:
The mission itself is just an ordinary SFC mission and requires nothing special. The Configuration Utility requires that you have the latest version of the Microsoft Foundation Class Libraries installed. Chances are high that you already have these files installed and don't have to worry about it. If you do need to update your version of the libraries, you can get them from Microsoft's web site.


Enjoy,
--
Scott Bruno
aka Captain Krumb, IKV Death's Hand
email: krumb@abac.com